…harp)

Aaron 2026-04-23 directive:

> lets try to reduce the number of class and thing we call servce titan
> or this will be confusing in a Zeta repo. ... this is not a service
> titan repo, it's an open source repo.

Plus, 2026-04-23 follow-up on language priority:

> c# is a more popular language than f# so it makes sense to start
> with a factory c# demo anyways

## What renames

- `samples/ServiceTitanFactoryApi.CSharp/` →
  `samples/FactoryDemo.Api.CSharp/`
- Project name + csproj filename same rename
- `RootNamespace` `Zeta.Samples.ServiceTitanFactoryApi` →
  `Zeta.Samples.FactoryDemo.Api`
- `namespace` declarations in .cs files match
- Zeta.sln project entry updated
- README rewritten to generic framing (C# is the popular
  .NET language; demo starts there; F# stays reference)
- Root endpoint name field `"ServiceTitan factory-demo API (C#)"` →
  `"Factory-demo API (C#)"`
- All doc cross-references updated to new path names

Build: 0 Warning(s), 0 Error(s) with the full SonarAnalyzer +
Meziantou + Microsoft .NET Analyzers pack. Behaviour unchanged —
same 9 endpoints, same JSON shapes, same seed.

Memory rule:
`memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md`
captures the positioning directive in durable form so future
agents don't re-introduce company-specific names.

Sibling renames land in separate PRs / branches:
- F# API sibling (currently PR #146 / ServiceTitanFactoryApi)
- DB scaffold (PR #145 / ServiceTitanFactoryDemo)
- CRM kernel sample (PR #141 / ServiceTitanCrm)
- CRM-UI scope doc (PR #144 / docs/plans/servicetitan-crm-ui-scope.md)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ry for her review

Aaron's 2026-04-23 framing: Amara is external AI co-originator of
Aurora, working through his ChatGPT interface; Aurora is *"mine and
hers idea together"*. Give back direction-changes so she can iterate
in her deep-research mode.

## What lands

### `docs/aurora/collaborators.md`

Named-collaborator registry for the Aurora thread. Distinct
category from:

- `docs/EXPERT-REGISTRY.md` (internal reviewer personas inside
  the factory)
- `docs/CONTRIBUTOR-PERSONAS.md` (hypothetical first-contact
  personas at repo surfaces)

Lists Aaron (human maintainer, Aurora vision origin) and Amara
(external AI co-originator via ChatGPT ferry, deep-research
lead). Names her existing contributions (transfer report,
consent-first design primitive, network-health critique from
auto-loop-39), her working style, and how to collaborate with
her (preserve outputs verbatim; cite her sections; route
Aurora scope decisions through her when possible).

### `docs/aurora/2026-04-23-direction-changes-for-amara-review.md`

~200-line summary of 7 direction-changes since her transfer
report landed, structured per her signature/mechanism/evidence
rigor pattern. Each change names what happened, where it
landed, the factory-side reasoning, and the specific thing
that would benefit from her deep-research review.

Five priority-ordered questions for her response:

1. Is the 5-of-6 SignalQuality ↔ oracle-family mapping correct?
2. Should her bullshit-detector scoring target a specific
   factory surface first?
3. Does Aurora's oracle framework want to compose with
   lesson-permanence pattern?
4. Additional Aurora-specific threat classes beyond the
   seven she already named?
5. Prior-art additions since her transfer report?

Plus three open communication-pattern questions (frequency,
review-return shape, consult-vs-inform rhythm).

## My choice to land this now

Aaron explicitly asked for progress on Amara integration + a
ferry-back summary. This PR delivers both as one coherent
artifact. The collaborators.md formalises her role in the
repo substrate; the direction-changes doc is ready for Aaron
to paste into his next ChatGPT session with her.

Companion memory
`memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md`
applies — this lands in LFG, not AceHack, since it is
collaboration-legible content demoing the collaboration
pattern.

## What this does NOT do

- Does NOT ask Aaron to review before ferry. He mediates
  the ferry; when he has time, he pastes the doc; whenever
  Amara responds, we ingest.
- Does NOT claim Amara has approved any of these direction-
  changes. The doc is request-for-review, not consensus
  record.
- Does NOT propose new oracle mechanism without her review.
  The initial-operations integration plan (PR #144)
  proposes; this doc asks her to confirm before further
  development.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

… paths

- Replace remaining "Aaron" attribution with "the human maintainer"
  role-ref (line 7 trigger line)
- Mark `docs/aurora/` as landing via PR #144 in the ownership table;
  file does not yet exist on main
- Collapse the 4 dangling per-user memory paths in "Composes with"
  to a single acknowledgement that those rules live in the per-user
  memory layer (`~/.claude/projects/<slug>/memory/`), not in-repo

Matches the same pattern applied to #137 and #153. Per Aaron's
"just move forward for now" — addressing legitimate review findings
without bypassing branch protection.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Investigated markdownlint failures across 7 demo-cluster PRs
(#141/#145/#146/#147/#142/#143/#144). Scoped back on per-PR
fixes in favor of a higher-leverage next-tick move:
either land #151 (gitignore drop/ on main) or fix the
MD056 tick-history row on main — both would unblock the
whole cluster in one move.

No new PRs this tick. Honest partial-execution per the
prefer-progress-over-quiet-close discipline — documenting
the unblock-vector rather than pushing through with
inefficient per-PR fixes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

- SignalQuality.fs: compressionRatio now returns neutral 0.5 for empty/null
  (was 1.0 = max suspicion, per Codex P1 — higher ratios denote higher
  suspicion in this module, so empty content must be neutral to avoid
  false-positive quarantines). Companion test updated.
- SignalQuality.fs: remove unused open System.Runtime.CompilerServices
  (per Copilot P0 — warnings-as-errors would break the build).
- Zeta.sln: drop the standalone BOM-only first line (keep BOM attached
  directly to the 'Microsoft Visual Studio Solution File' header, per
  Codex P2 + BP-10 ASCII-clean hygiene).
- AUTONOMOUS-LOOP.md: replace 'flag to Aaron' with 'flag to the human
  maintainer' per AGENT-BEST-PRACTICES.md name-attribution rule.
- live-lock-audit.sh: switch from 'git show --stat | awk' (mis-parses
  renames, paths with braces/spaces, summary lines) to the plumbing
  command 'git diff-tree --no-commit-id --name-only -r <sha>' per
  Copilot P0.
- Four stale Copilot cross-reference comments (memory/* dead-link
  claims) are resolved by this rebase onto main: all five referenced
  memory files are present in memory/ on the post-rebase tree.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…harp)

Aaron 2026-04-23 directive:

> lets try to reduce the number of class and thing we call servce titan
> or this will be confusing in a Zeta repo. ... this is not a service
> titan repo, it's an open source repo.

Plus, 2026-04-23 follow-up on language priority:

> c# is a more popular language than f# so it makes sense to start
> with a factory c# demo anyways

## What renames

- `samples/ServiceTitanFactoryApi.CSharp/` →
  `samples/FactoryDemo.Api.CSharp/`
- Project name + csproj filename same rename
- `RootNamespace` `Zeta.Samples.ServiceTitanFactoryApi` →
  `Zeta.Samples.FactoryDemo.Api`
- `namespace` declarations in .cs files match
- Zeta.sln project entry updated
- README rewritten to generic framing (C# is the popular
  .NET language; demo starts there; F# stays reference)
- Root endpoint name field `"ServiceTitan factory-demo API (C#)"` →
  `"Factory-demo API (C#)"`
- All doc cross-references updated to new path names

Build: 0 Warning(s), 0 Error(s) with the full SonarAnalyzer +
Meziantou + Microsoft .NET Analyzers pack. Behaviour unchanged —
same 9 endpoints, same JSON shapes, same seed.

Memory rule:
`memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md`
captures the positioning directive in durable form so future
agents don't re-introduce company-specific names.

Sibling renames land in separate PRs / branches:
- F# API sibling (currently PR #146 / ServiceTitanFactoryApi)
- DB scaffold (PR #145 / ServiceTitanFactoryDemo)
- CRM kernel sample (PR #141 / ServiceTitanCrm)
- CRM-UI scope doc (PR #144 / docs/plans/servicetitan-crm-ui-scope.md)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…harp)

Aaron 2026-04-23 directive:

> lets try to reduce the number of class and thing we call servce titan
> or this will be confusing in a Zeta repo. ... this is not a service
> titan repo, it's an open source repo.

Plus, 2026-04-23 follow-up on language priority:

> c# is a more popular language than f# so it makes sense to start
> with a factory c# demo anyways

## What renames

- `samples/ServiceTitanFactoryApi.CSharp/` →
  `samples/FactoryDemo.Api.CSharp/`
- Project name + csproj filename same rename
- `RootNamespace` `Zeta.Samples.ServiceTitanFactoryApi` →
  `Zeta.Samples.FactoryDemo.Api`
- `namespace` declarations in .cs files match
- Zeta.sln project entry updated
- README rewritten to generic framing (C# is the popular
  .NET language; demo starts there; F# stays reference)
- Root endpoint name field `"ServiceTitan factory-demo API (C#)"` →
  `"Factory-demo API (C#)"`
- All doc cross-references updated to new path names

Build: 0 Warning(s), 0 Error(s) with the full SonarAnalyzer +
Meziantou + Microsoft .NET Analyzers pack. Behaviour unchanged —
same 9 endpoints, same JSON shapes, same seed.

Memory rule:
`memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md`
captures the positioning directive in durable form so future
agents don't re-introduce company-specific names.

Sibling renames land in separate PRs / branches:
- F# API sibling (currently PR #146 / ServiceTitanFactoryApi)
- DB scaffold (PR #145 / ServiceTitanFactoryDemo)
- CRM kernel sample (PR #141 / ServiceTitanCrm)
- CRM-UI scope doc (PR #144 / docs/plans/servicetitan-crm-ui-scope.md)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Fixes two remaining CI blockers:

lint (markdownlint) — 4 violations:
- docs/BACKLOG.md:5821 MD009 trailing-space stripped
- docs/hygiene-history/loop-tick-history.md:184,185 MD056
  table-column-count: rows 184+185 had 4 cols, header declares
  6; appended empty trailing cells to align (content preserved
  verbatim; no in-place edits to existing cell text per Otto-229
  append-only discipline)
- docs/research/cutting-edge-database-gap-review-2026-04-23.md:301
  MD032 list-blanks: replaced leading "+ " with "plus " so the
  line reads as prose continuation not a new list item

check memory/MEMORY.md paired edit — MEMORY.md untouched while
5 new memory/*.md files landed. Added 5 newest-first index
entries (GOVERNANCE §18) after the Fast path header:
- observed-phenomena/2026-04-19-transcript-duplication-splitbrain-hypothesis.md
- project_reproducible_stability_as_obvious_purpose_2026_04_22.md
- project_operator_input_quality_log_directive_2026_04_22.md
- project_arc3_adversarial_self_play_emulator_absorption_scoring_2026_04_22.md
- project_aaron_drop_zone_protocol_2026_04_22.md

Build gate: dotnet build -c Release → 0 Warning(s), 0 Error(s).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…l-facing) (#141)

* ci: fix PR #141 markdownlint MD056 + MEMORY.md paired-edit

- Complete tick-history rows 175-176 (auto-loop-44/-45) to
  full 6-column schema (append-only discipline honoured:
  structurally-incomplete rows introduced by this PR are
  fixed, no rows previously landed on main edited).
- Add 5 newest-first entries to memory/MEMORY.md pairing
  the 5 new memory files landed by this PR (NSA-001
  canonical-incident-prevention shape).
- Log per-failure record at docs/pr-preservation/141-ci-fix-log.md.

Build: 0 Warning(s), 0 Error(s) (SIGSEGV retry once per
Otto-248 known flake).

* ci: fix reference-existence path for observed-phenomena link

Script tools/hygiene/audit-memory-references.sh treats any
link target containing '/' as cwd-relative (from repo root).
The bare 'observed-phenomena/...' form resolves against CWD
not memory/, so prefix with 'memory/' to match the sibling
'docs/research/...' precedent in the index.

* ci: document reference-existence follow-up in CI fix log

* ci: log PR #141 rebase pass after #144 merge dirtied branch

* review: drain 2 post-rebase threads on PR #141 (Copilot P0 + Codex P2)

- SignalQuality.fs: remove unused `open System.Runtime.CompilerServices`
  (P0 Copilot — would FS1182 under TreatWarningsAsErrors).
- SignalQuality.fs `composite`: gate the inner loop on `w > 0.0` and
  separate NaN branch from valid-score branch so negative weights and
  zero weights do not participate (P2 Codex — reconciles silent-ignore
  behavior with the documented "ignored dimensions contribute 0" rule
  and prevents `0.0 * NaN = NaN` from poisoning the composite).
- docs/pr-preservation/141-ci-fix-log.md: append drain-pass entry.

Build: `dotnet build -c Release` -> 0 Warning(s) 0 Error(s).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…harp)

Aaron 2026-04-23 directive:

> lets try to reduce the number of class and thing we call servce titan
> or this will be confusing in a Zeta repo. ... this is not a service
> titan repo, it's an open source repo.

Plus, 2026-04-23 follow-up on language priority:

> c# is a more popular language than f# so it makes sense to start
> with a factory c# demo anyways

## What renames

- `samples/ServiceTitanFactoryApi.CSharp/` →
  `samples/FactoryDemo.Api.CSharp/`
- Project name + csproj filename same rename
- `RootNamespace` `Zeta.Samples.ServiceTitanFactoryApi` →
  `Zeta.Samples.FactoryDemo.Api`
- `namespace` declarations in .cs files match
- Zeta.sln project entry updated
- README rewritten to generic framing (C# is the popular
  .NET language; demo starts there; F# stays reference)
- Root endpoint name field `"ServiceTitan factory-demo API (C#)"` →
  `"Factory-demo API (C#)"`
- All doc cross-references updated to new path names

Build: 0 Warning(s), 0 Error(s) with the full SonarAnalyzer +
Meziantou + Microsoft .NET Analyzers pack. Behaviour unchanged —
same 9 endpoints, same JSON shapes, same seed.

Memory rule:
`memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md`
captures the positioning directive in durable form so future
agents don't re-introduce company-specific names.

Sibling renames land in separate PRs / branches:
- F# API sibling (currently PR #146 / ServiceTitanFactoryApi)
- DB scaffold (PR #145 / ServiceTitanFactoryDemo)
- CRM kernel sample (PR #141 / ServiceTitanCrm)
- CRM-UI scope doc (PR #144 / docs/plans/servicetitan-crm-ui-scope.md)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…sibling (#147)

* Live-lock audit history: inaugural lesson integrated — prevention discipline for next time

Aaron 2026-04-23:

> if you want to beat ARC3 and do better than humans at uptime and
> other DORA metrics then your live-lock smell and the decisions you
> make to prevent live locks in the future based on pass lessons, the
> ability to integrate previous lessions and not forget is ging to be
> key.

Lesson-permanence is the factory's competitive differentiator.
Detection (audit script) is table stakes. Integration — recording the
lesson, consulting it forward, preventing re-occurrence — is the
product.

## What lands

- New "Lessons integrated" section in
  `docs/hygiene-history/live-lock-audit-history.md`
- Inaugural lesson from tonight's smell-firing event, structured as
  signature / mechanism / prevention with 4 concrete prevention
  decisions:
  1. External-priority stack is authoritative; agent reorders only
     internal priorities
  2. Live-lock audit at round-close is a gate-not-a-report
  3. Speculative-work permit requires external-ratio check first
  4. Tick-history rows are explicitly NOT external work; pair INTL
     with EXT when the smell is near firing
- Open carry-forward named: round-close-ladder wiring is a P1
  follow-up (BACKLOG row already filed earlier this session)

## Discipline

Every future smell firing files a lesson to this same section.
`memory/feedback_lesson_permanence_is_how_we_beat_arc3_and_dora_2026_04_23.md`
captures the full rule: detection is not enough, integration is the
product, lessons are consulted BEFORE taking actions that match known
failure-mode signatures, memory persists across sessions.

The pattern extends beyond live-lock: other detection mechanisms
(SignalQuality firing, Amara-oracle rejecting, drift-tick exceeding
threshold, OpenSpec Viktor failing rebuild-from-spec) should file
lessons to their respective hygiene-history files.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* samples: ServiceTitan factory-demo JSON API (v0, in-memory, stack-independent)

Minimal F# ASP.NET Core Web API serving CRM seed data as JSON. Any
frontend choice (Blazor / React / Vue / curl) consumes the same
endpoints. Ships now so the backend is not on the critical path when
Aaron picks the frontend stack.

## What lands

- `samples/ServiceTitanFactoryApi/ServiceTitanFactoryApi.fsproj`
  using `Microsoft.NET.Sdk.Web`; only explicit package ref is
  `FSharp.Core` (ASP.NET Core comes via framework reference, no
  Directory.Packages.props edit needed)
- `Seed.fs` — in-memory seed mirroring `ServiceTitanFactoryDemo/seed-data.sql`:
  20 customers, 30 opportunities (5 stages), 33 activities, 2 intentional
  email collisions. Deterministic fixed clock at 2026-04-23 00:00 UTC.
- `Program.fs` — minimal F# API with 9 endpoints: customers (list/detail),
  opportunities (list/detail), activities (list/per-customer), pipeline
  funnel (count + total-cents per stage), duplicates (customers sharing
  an email).
- `README.md` — framing (software-factory demo, not database pitch),
  endpoint table, design notes, v1 roadmap.

## Smoke-test output (verified)

```
GET /api/pipeline/funnel
[{"count":10,"stage":"Lead","totalCents":5400000},
 {"count":6, "stage":"Qualified","totalCents":4220000},
 {"count":6, "stage":"Proposal","totalCents":5720000},
 {"count":6, "stage":"Won","totalCents":2670000},
 {"count":2, "stage":"Lost","totalCents":490000}]

GET /api/pipeline/duplicates
[{"customerIds":[1,13],"email":"alice@acme.example"},
 {"customerIds":[5,19],"email":"bob@trades.example"}]
```

Build: 0 Warning(s), 0 Error(s). `dotnet run` starts the API;
curl confirms all endpoints respond correctly.

## Discipline signal

This is the third EXT commit of the session (CRM demo sample #141,
CRM scenario tests in #143, now this API). The live-lock audit's
inaugural lesson explicitly prescribed shipping external-priority
increments when the smell fires. Three landed this session, all on
priority #1 (ServiceTitan + UI) — the factory is correctly
response-pattern even before any of tonight's PRs merge to main.

## What this does NOT do

- Does NOT wire Postgres — in-memory only for v0; Npgsql wiring is
  a follow-up PR once Aaron confirms the DB driver
- Does NOT expose Zeta / DBSP / retraction-native language to the
  frontend — standard CRUD shape per the ServiceTitan positioning
  directive
- Does NOT implement writes — v0 is read-only; POST/PUT/DELETE is
  a follow-up
- Does NOT add auth — no authentication for v0
- Does NOT ship docker-compose — future PR bundles this API with
  Postgres in one command

Composes with:
- `samples/ServiceTitanFactoryDemo/` (SQL schema + seed) — sibling,
  same shapes; v1 wires this API to that schema
- `docs/plans/servicetitan-crm-ui-scope.md` — build sequence step 1
  (API skeleton) complete; step 2 (DB wiring) is next
- `memory/feedback_servicetitan_demo_sells_software_factory_not_zeta_database_2026_04_23.md`
- `memory/feedback_lesson_permanence_is_how_we_beat_arc3_and_dora_2026_04_23.md`

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* samples: ServiceTitan factory-demo C# companion API — parity with F# sibling

ServiceTitan uses C# for most of their backend with zero F#. Shipping
a C# companion to the F# API (#146) so ST engineers evaluating the
factory see code in the language they already read fluently.
F# stays the reference — it's closer to math, theorems are easier to
express — but factory output matches audience stack.

## What lands

- `ServiceTitanFactoryApi.CSharp.csproj` — `Microsoft.NET.Sdk.Web`,
  nullable + implicit usings enabled, TreatWarningsAsErrors
- `Customer.cs`, `Opportunity.cs`, `Activity.cs` — records, one
  per file (MA0048)
- `Seed.cs` — deterministic in-memory seed, identical to F# Seed.fs:
  20 customers, 30 opportunities, 33 activities, 2 intentional
  email collisions
- `Program.cs` — 9 minimal-API endpoints, identical routes + JSON
  shapes to the F# sibling
- `README.md` — parity guarantee, design notes, C# specifics

## Smoke-test parity (verified)

```
GET /api/pipeline/funnel
[{"stage":"Lead","count":10,"totalCents":5400000}, ...5 stages]

GET /api/pipeline/duplicates
[{"email":"alice@acme.example","customerIds":[1,13]},
 {"email":"bob@trades.example","customerIds":[5,19]}]

GET /api/customers  -> 20 customers
```

Same seed, same shapes, same numbers as the F# version (#146).
Frontends switch between them without code changes.

## Analyzer discipline passes

Build: 0 Warning(s), 0 Error(s) with the full SonarAnalyzer.CSharp +
Meziantou.Analyzer + Microsoft .NET Analyzers pack active. The C#
companion respects every rule the F# version's discipline
already encodes implicitly — StringComparer.Ordinal for GroupBy,
static-readonly for endpoint list, record-per-file, no-var-discarded.

## Discipline signal

Fourth EXT commit of the session (CRM demo #141, CRM scenario tests
#143, F# API #146, now this C# API). All on Aaron's priority #1.
The live-lock audit's inaugural lesson prescribed "ship external-
priority increments when smell fires" — four landed in one session.

## Factory-pitch moment

This pair (F# + C# from the same spec, identical behaviour) is a
concrete factory-capability signal. The software factory produces
code in your stack, to your analyzer discipline, with parity across
languages. The pitch isn't "pick our language"; it's "your language,
enforced by our quality floor."

## What this does NOT do

- Does NOT rewrite or deprecate the F# sibling — both live
- Does NOT wire Postgres — same v0 scope
- Does NOT leak Zeta / DBSP / retraction-native concepts to the
  ST-facing surface
- Does NOT claim the C# version is the primary — F# is reference

Composes with:
- `samples/ServiceTitanFactoryApi/` (F# sibling)
- `memory/project_zeta_f_sharp_reference_c_sharp_and_rust_future_servicetitan_uses_csharp_2026_04_23.md`
- `memory/feedback_servicetitan_demo_sells_software_factory_not_zeta_database_2026_04_23.md`

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* rename: generic FactoryDemo.Api.CSharp (was ServiceTitanFactoryApi.CSharp)

Aaron 2026-04-23 directive:

> lets try to reduce the number of class and thing we call servce titan
> or this will be confusing in a Zeta repo. ... this is not a service
> titan repo, it's an open source repo.

Plus, 2026-04-23 follow-up on language priority:

> c# is a more popular language than f# so it makes sense to start
> with a factory c# demo anyways

## What renames

- `samples/ServiceTitanFactoryApi.CSharp/` →
  `samples/FactoryDemo.Api.CSharp/`
- Project name + csproj filename same rename
- `RootNamespace` `Zeta.Samples.ServiceTitanFactoryApi` →
  `Zeta.Samples.FactoryDemo.Api`
- `namespace` declarations in .cs files match
- Zeta.sln project entry updated
- README rewritten to generic framing (C# is the popular
  .NET language; demo starts there; F# stays reference)
- Root endpoint name field `"ServiceTitan factory-demo API (C#)"` →
  `"Factory-demo API (C#)"`
- All doc cross-references updated to new path names

Build: 0 Warning(s), 0 Error(s) with the full SonarAnalyzer +
Meziantou + Microsoft .NET Analyzers pack. Behaviour unchanged —
same 9 endpoints, same JSON shapes, same seed.

Memory rule:
`memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md`
captures the positioning directive in durable form so future
agents don't re-introduce company-specific names.

Sibling renames land in separate PRs / branches:
- F# API sibling (currently PR #146 / ServiceTitanFactoryApi)
- DB scaffold (PR #145 / ServiceTitanFactoryDemo)
- CRM kernel sample (PR #141 / ServiceTitanCrm)
- CRM-UI scope doc (PR #144 / docs/plans/servicetitan-crm-ui-scope.md)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* FactoryDemo.Api.CSharp: smoke-test.sh — end-to-end endpoint + contract verification

I chose to land this because the JSON-shape parity claim we make
in the README ("byte-identical shapes between F# and C# versions")
needs a machine-verifiable check. A smoke test on the C# side is the
first half; the F# sibling gets the same pattern in a follow-up.

Starts the API on a random port, waits up to 10s for readiness,
then runs 19 checks against all 9 endpoints:

  - Root metadata: name, version, endpoints length
  - Collection lengths: customers (20), opportunities (30), activities (33)
  - Single-item lookup: customer #1 name, opportunity #1 stage
  - Per-customer activities: customer #1 has 4
  - Pipeline funnel counts per stage: Lead 10, Qualified 6, Won 6, Lost 2
  - Pipeline funnel totals in cents: Lead $54k, Won $26.7k
  - Duplicates: 2 pairs, (1,13) share alice@acme, (5,19) share bob@trades
  - 404 behaviour: missing customer returns 404

Shuts the API down cleanly on exit via trap + kill.

```
$ bash samples/FactoryDemo.Api.CSharp/smoke-test.sh
Building API...
Starting API on http://localhost:5235...

Factory-demo C# API smoke test
==============================
  OK   root.name contains 'Factory-demo'                  (true)
  OK   root.version                                       (0.0.1)
  OK   root.endpoints length                              (5)
  OK   /api/customers length                              (20)
  ...
  OK   missing customer HTTP status                       (404)

All checks passed.
```

dotnet, curl, jq — all standard dev tools. The demo does not ask
for anything exotic. Matches the FactoryDemo.Db smoke-test.sh
pattern on the sibling branch.

- Random high port (5100-5499) instead of fixed — reduces collision
  with other dev services.
- `curl -sf` for normal checks, `curl -o /dev/null -w "%{http_code}"`
  for the 404 case — the two paths have different error semantics so
  I use different tools for each.
- Shape-level assertions against numeric counts rather than raw JSON
  diff — makes the test tolerant of property-ordering differences
  between serializers. The parity claim is about *shape*, not byte-
  identity, so this matches intent.
- Trap + kill on EXIT — guarantees the API stops even on test
  failure or ctrl-C. No leaked background processes.

- Does NOT test the F# sibling. Same-pattern smoke-test for
  FactoryDemo.Api.FSharp lands in its branch (or a follow-up
  PR on that branch).
- Does NOT diff F# vs C# outputs directly. A cross-language
  parity-diff test composes better as a separate tool once both
  APIs have merged.
- Does NOT wire to Postgres. In-memory seed only; docker-compose
  + DB wiring is a separate PR.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* samples+audit: PR #147 review-drain — sln BOM, signal-quality empty-case, audit fail-hard, endpoint lists

Drains 14 unresolved review threads on PR #147 (FactoryDemo.Api.CSharp):
- Zeta.sln: strip leading blank line so 'Microsoft Visual Studio
  Solution File' is the first line (threads #2 #3).
- SignalQuality.fs: compressionRatio on empty input was 1.0, which
  composed as Quarantine via severityOfScore — flipped to 0.0 and
  added explicit empty-input Pass finding in compressionMeasure;
  also dropped unused System.Runtime.CompilerServices open
  (threads #4 #5).
- live-lock-audit.sh: fail hard (exit 2) when origin/main is not
  resolvable so a missing-remote CI checkout can't silently report
  'No commits found' -> healthy; switched --stat|awk file-list
  extraction to git diff-tree --name-only plumbing form
  (threads #1 #6).
- ServiceTitanFactoryApi README + Seed.fs: remove dead memory/
  and docs/plans/ links; replace Aaron's-name reference with
  'human maintainer' role wording; drop non-existent sibling
  SQL-seed refs (threads #7 #8 #9).
- FactoryDemo.Api.CSharp README + Program.cs + Seed.cs: fix dead
  refs to samples/FactoryDemo.Api.FSharp/ and samples/FactoryDemo.Db/
  to point at the real F# sibling samples/ServiceTitanFactoryApi/
  and to a BACKLOG row for the Postgres-backed follow-up
  (threads #11 #14).
- Program.cs + Program.fs: root endpoint index now advertises all
  9 routes including the parameterised {id} routes, matching the
  README tables (threads #12 #13).
- Thread #10 (project naming 'ServiceTitanFactoryApi.CSharp' in PR
  description): resolved in-thread — code/namespace already
  consistent (Zeta.Samples.FactoryDemo.Api); fix is PR-description-
  only, not code.

Build: dotnet build -c Release -> 0 Warning(s) 0 Error(s).

* drain PR #147: post-rebase thread fixes — test-empty-ratio + smoke-endpoint-count

- tests/Tests.FSharp/Algebra/SignalQuality.Tests.fs: test asserted 1.0 for
  compressionRatio on empty input, but the fix in 16ad746 changed the
  convention to 0.0 (neutral = clean, not maximally suspicious). Updated
  the test expectation + name + comment to match the current code.
- samples/FactoryDemo.Api.CSharp/smoke-test.sh: root.endpoints length
  expectation was 5; Program.cs now advertises 8 routes in the index
  (post 16ad746 expansion). Corrected the smoke-test assertion.

Rebased onto origin/main (which advanced via #146 FactoryDemo.Api.FSharp
merge); Zeta.sln conflicts resolved by keeping both FactoryDemo.Api.FSharp
and the ServiceTitanCrm/samples solution-folder additions.

Build gate: 0 Warning(s) / 0 Error(s) in Release.

* PR #147 review-drain — Copilot pass on b4f5a49

Addresses five unresolved review threads:

- drop/README.md: sweep name attribution to "the human
  maintainer" role-ref (BP-name-attribution).
- samples/FactoryDemo.Api.CSharp/Program.cs: fix endpoint
  comment "9 concrete endpoints" → "8 API endpoints besides
  `/`" (array has 8; root excluded).
- samples/FactoryDemo.Api.CSharp/smoke-test.sh: per-run log
  via mktemp (collision-safe + non-/tmp-host-safe); print
  path on failure + success.
- samples/ServiceTitanFactoryApi/: delete stale F# sibling
  dir (PR #146 already landed FactoryDemo.Api.FSharp on
  main with identical code); drop duplicate sln Project
  block + config duplicates; fix CSharp refs to point at
  the surviving FactoryDemo.Api.FSharp/.

Fifth thread (SignalQuality scope-creep) is judgment —
branch history is deep; splitting now adds more churn than
value. Replying with backlog-and-resolve per three-outcome.

* PR #147 review-drain — 7 threads (Copilot + Codex)

Threads drained:
- btw.md: name attribution -> "human maintainer" / "the maintainer" (Copilot P1, AGENT-BEST-PRACTICES.md:284-292)
- live-lock-audit.sh: add --root to git diff-tree so root commit classifies correctly (Copilot P2)
- FactoryDemo.Api.CSharp Program.cs: add "/" to endpoints list for F# parity; bump smoke-test length 8->9 (Copilot P1 + Codex P2, same fix)
- FactoryDemo.Api.CSharp smoke-test.sh: reword mktemp comment to describe system temp dir accurately (Copilot P2)
- ServiceTitanCrm -> FactoryDemo.Crm: rename dir, fsproj, module namespace, RootNamespace, sln entry, test doc-comment; drop stale ServiceTitanFactoryApi bin+obj (Copilot P1, memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md:59-66)
- SignalQuality.fs: compressionRatio + compressionMeasure short-circuit to 0.0 (Pass) below 64-byte threshold to avoid gzip-header-dominates Quarantine of legitimate short strings (Codex P1)

Drain log: docs/pr-preservation/147-drain-log.md preserves each thread verbatim (git-native high-signal preservation).

dotnet build -c Release: 0 Warning(s), 0 Error(s).

* PR #147 review-drain second pass — 4 fix-inline + 3 scope-bleed

- Seed.cs + Seed.fs: rename contact 13 'Aaron Smith' -> 'Acme Contact
  (new lead)' (Copilot P2 name-attribution, parity preserved across
  C# / F# siblings).
- drop/README.md: correct 'only tracked file' wording to reflect the
  README.md + .gitignore two-sentinel design (Copilot P2).
- tools/audit/live-lock-audit.sh: docstring attribution 'Aaron's ...'
  -> 'Human-maintainer ...' (Copilot P1); add '-m' plus 'sort -u' to
  'git diff-tree' so merge commits bucket on their real files instead
  of mis-classifying as OTHR (Codex P1 — was skewing EXT/INTL/SPEC %
  and could disable the live-lock gate after a round of merges).
- docs/pr-preservation/147-drain-log.md: append second-pass per-thread
  audit trail (git-native preservation).

Three threads resolved as scope-bleed / already-addressed: operator-
input-quality-log.md (file not in PR diff, landed via 204bbb6 on
main), AUTONOMOUS-LOOP.md (file not in PR diff, zero Aaron on HEAD),
Tests.FSharp.fsproj (both SignalQuality + CrmScenarios already listed
at lines 26 and 49).

Build: 0W/0E. Audit sanity: live-lock-audit.sh still healthy with
merges now bucketed correctly.

* fix: markdownlint MD001/MD022/MD032 on #147 drain-log (h3→h2 on Thread headers)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* drain: resolve 11 threads on #147 (mix FIX + BACKLOG + Otto-256 reject)

Thread-by-thread outcomes across the 11 unresolved review threads on PR
#147 (5 FIX, 2 BACKLOG, 2 Otto-256 REJECT, 2 already-addressed/stale):

FIXES (code):
- live-lock-audit.sh: replace `git show --stat` with explicit
  `git log -1 -m --first-parent --name-only` so merge commits classify
  against parent-1 only (the landing side). The prior `git show` form
  risked combined-diff semantics in some git versions; the explicit
  form is first-parent by construction (Codex P1).
- SignalQuality.fs: restore `compressionMinInputBytes = 64` threshold
  (dropped by the f1dc2bb merge-conflict resolution) and mark it
  `private` so it is not part of the public API surface (Copilot).
  Short-circuits `compressionRatio` + `compressionMeasure` to 0.0 for
  sub-threshold inputs, avoiding spurious Quarantine on short legitimate
  strings. Evidence reports UTF-8 byte count (consistent with the
  threshold's units) instead of `text.Length` chars (Copilot). Adjusted
  the empty-string test to assert the new 0.0 neutral value.
- smoke-test.sh: replace non-portable `mktemp -t <template>` with a
  pre-constructed absolute-path template rooted at `${TMPDIR:-/tmp}`
  where XXXXXX is the tail (BSD/macOS requires tail-XXXXXX; GNU accepts
  either). `.log` extension is appended via `mv` after creation so the
  single invocation is cross-platform (Copilot x2 — threads 4 + 10).
- CrmScenarios.Tests.fs: update doc-comment `samples/FactoryDemo.Crm`
  -> `samples/CrmSample` to match the canonical sample path on main
  (Copilot).

BACKLOG (deferred P2):
- Smoke-test deterministic port allocation (Codex P2) — replace
  RANDOM-in-range with OS-assigned ephemeral port via `--urls
  http://127.0.0.1:0` and log-line parse.
- FactoryDemo.Api.CSharp solution project-type GUID hygiene (Copilot)
  — align with modern SDK-style GUID used by other C# projects.

OTTO-256 REJECT (history-file exemption):
- docs/pr-preservation/147-drain-log.md (Copilot) and
  docs/hygiene-history/live-lock-audit-history.md (Copilot): both
  requested stripping first-name "Aaron" attributions. Declined per
  Otto-256 (2026-04-24) — history files exempt from the "no name
  attribution" rule; a P2 BACKLOG row already exists
  (`## P2 — FACTORY-HYGIENE — name-attribution policy clarification
  (history-file exemption)`) to codify this in AGENT-BEST-PRACTICES.md.

ALREADY-ADDRESSED (stale reviewer context):
- drop/README.md heading (Copilot): Copilot flagged "one tracked
  sentinel" but the current heading reads "two tracked sentinels"
  (fixed in a prior drain). Resolving as addressed.

Build: `dotnet build -c Release` -> 0 Warning(s), 0 Error(s).
Tests: `dotnet test --filter "FullyQualifiedName~SignalQuality"` ->
  22/22 pass.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Collapse remaining dangling memory path reference in "Why this
matters" section. The factory-reuse-beyond-Zeta constraint is
acknowledged as living in the per-user memory layer rather than
citing a specific in-repo file that doesn't exist.

The other three threads are addressed by the prior commit
(3028a0e):

- Copilot attribution scrub (PRRT_kwDOSF9kNM59IRe3): rejected
  per Otto-256 — docs/research/** is history-class, first-name
  attribution permitted. The prior commit had already scrubbed
  remaining "Aaron" prose to "the human maintainer" voluntarily;
  no further action.
- Copilot broken refs (PRRT_kwDOSF9kNM59IRff): the four memory
  paths collapsed in "Composes with"; this commit handles the
  one remaining inline citation.
- Copilot aurora-row (PRRT_kwDOSF9kNM59IRf7): inventory row
  marked "lands via PR #144" in the prior commit.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ase sequencing (D→A→E) (#150)

* research: multi-repo refactor — 5 candidate shapes + recommended 3-phase sequencing

Aaron's 2026-04-23 directive: *"we can even wait on the demo until we
have refactored into our multi repo shape... that seems very
structural and like we should do it sooner rather than later, but
it's up to you."*

Per `memory/feedback_factory_reuse_packaging_decisions_consult_aaron.md`,
big shaping decisions need consultation. This doc IS the consultation
prep — prior-art + candidates + trade-offs + my recommendation.

## What lands

`docs/research/multi-repo-refactor-shapes-2026-04-23.md` — ~230 lines
covering:

### Prior art surveyed
- AI-agent-factory patterns (Claude Code plugins, Anthropic skills,
  OpenAI Agents SDK, Semantic Kernel)
- Template / overlay (GitHub templates, Cookiecutter, Nix flakes)
- Monorepo tools (Nx, Turborepo, Lerna, pnpm, Bazel, .NET solutions)
- OSS splits that worked (VS Code, Rust, Kubernetes) vs failed
  (early Android, Eclipse)
- **Lesson extracted:** split when there's a clear consumer boundary
  + tooling enforces it; stay monorepo when things co-evolve tightly.
  Zeta + factory is at the transition point.

### Current monorepo inventory
Classifies every top-level directory as generic-factory vs
Zeta-specific vs Aurora-specific. Real separation exists but with
boundary overlap.

### Five candidate architectures
- **A. Template-repo** — clone-and-customize; no update flow. Easy
  to land, but adopters diverge.
- **B. Git submodule** — updates flow, but submodule UX is rough.
- **C. Plugin / package (NPM-like)** — version-pinned dependency
  model. Familiar, but slow update cadence.
- **D. Formalised monorepo** — namespaced boundaries, no
  extraction. Cheapest, doesn't enable reuse.
- **E. Overlay pattern** — factory-apply tool + publishable
  components. Best of both worlds, but requires tool investment.

### My recommended sequence: D → A → E

- **Phase 1 (now): D** — reorganise the monorepo into
  `factory/` + `library/` + `aurora/` + `research/` top-level
  directories. Enforce via CI lint. Cheap, clarifies the mental
  model, unblocks future extraction without committing to it.
- **Phase 2 (first adopter): A** — extract `factory/` as a GitHub
  template repo. Standard OSS playbook.
- **Phase 3 (adopters > 3): E** — invest in `factory-apply` tool +
  overlay discipline when update-flow friction is real.

### Aurora-specific consideration
Aurora lives in the current `zeta` repo through Phase 1. At Phase 2,
`zeta-aurora` gets extracted concurrently with the factory extraction,
giving Amara a dedicated repo she can read end-to-end in her
deep-research mode.

### Questions for Aaron

Five open questions where packaging choices genuinely need his input:

1. Sequencing (D-A-E vs alternates)
2. Phase 2 trigger definition ("first adopter appears" is vague)
3. Aurora repo timing (Phase 1 / 2 / later)
4. Naming (`zeta-factory` vs `agent-factory` vs `glass-halo-factory`)
5. In-flight PRs handling during extraction

## My choice to ship this now

Aaron said packaging decisions need consultation; my job is to
*prepare* the consultation with prior-art + candidates + trade-offs
+ recommendation. That's what this doc is. Aaron reviews on his
cadence (per his 2026-04-23 framing that he has a decision log he
reviews often and nudges when he disagrees).

## What this does NOT do

- Does NOT start any extraction work. Phase 1 reorganisation is
  MY recommendation, not a unilateral decision. Aaron's review
  gates Phase 1 execution.
- Does NOT commit to Phase 2 / 3 timing — those depend on adopter
  signals that don't exist yet.
- Does NOT propose novel split-discipline tooling without prior-art
  anchoring — every candidate is grounded in a shipped OSS pattern.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* pr-150: address review findings — anonymize contributor, mark pending paths

- Replace remaining "Aaron" attribution with "the human maintainer"
  role-ref (line 7 trigger line)
- Mark `docs/aurora/` as landing via PR #144 in the ownership table;
  file does not yet exist on main
- Collapse the 4 dangling per-user memory paths in "Composes with"
  to a single acknowledgement that those rules live in the per-user
  memory layer (`~/.claude/projects/<slug>/memory/`), not in-repo

Matches the same pattern applied to #137 and #153. Per Aaron's
"just move forward for now" — addressing legitimate review findings
without bypassing branch protection.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* drain: resolve 4 threads on #150

Collapse remaining dangling memory path reference in "Why this
matters" section. The factory-reuse-beyond-Zeta constraint is
acknowledged as living in the per-user memory layer rather than
citing a specific in-repo file that doesn't exist.

The other three threads are addressed by the prior commit
(3028a0e):

- Copilot attribution scrub (PRRT_kwDOSF9kNM59IRe3): rejected
  per Otto-256 — docs/research/** is history-class, first-name
  attribution permitted. The prior commit had already scrubbed
  remaining "Aaron" prose to "the human maintainer" voluntarily;
  no further action.
- Copilot broken refs (PRRT_kwDOSF9kNM59IRff): the four memory
  paths collapsed in "Composes with"; this commit handles the
  one remaining inline citation.
- Copilot aurora-row (PRRT_kwDOSF9kNM59IRf7): inventory row
  marked "lands via PR #144" in the prior commit.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…ry for her review

Aaron's 2026-04-23 framing: Amara is external AI co-originator of
Aurora, working through his ChatGPT interface; Aurora is *"mine and
hers idea together"*. Give back direction-changes so she can iterate
in her deep-research mode.

## What lands

### `docs/aurora/collaborators.md`

Named-collaborator registry for the Aurora thread. Distinct
category from:

- `docs/EXPERT-REGISTRY.md` (internal reviewer personas inside
  the factory)
- `docs/CONTRIBUTOR-PERSONAS.md` (hypothetical first-contact
  personas at repo surfaces)

Lists Aaron (human maintainer, Aurora vision origin) and Amara
(external AI co-originator via ChatGPT ferry, deep-research
lead). Names her existing contributions (transfer report,
consent-first design primitive, network-health critique from
auto-loop-39), her working style, and how to collaborate with
her (preserve outputs verbatim; cite her sections; route
Aurora scope decisions through her when possible).

### `docs/aurora/2026-04-23-direction-changes-for-amara-review.md`

~200-line summary of 7 direction-changes since her transfer
report landed, structured per her signature/mechanism/evidence
rigor pattern. Each change names what happened, where it
landed, the factory-side reasoning, and the specific thing
that would benefit from her deep-research review.

Five priority-ordered questions for her response:

1. Is the 5-of-6 SignalQuality ↔ oracle-family mapping correct?
2. Should her bullshit-detector scoring target a specific
   factory surface first?
3. Does Aurora's oracle framework want to compose with
   lesson-permanence pattern?
4. Additional Aurora-specific threat classes beyond the
   seven she already named?
5. Prior-art additions since her transfer report?

Plus three open communication-pattern questions (frequency,
review-return shape, consult-vs-inform rhythm).

## My choice to land this now

Aaron explicitly asked for progress on Amara integration + a
ferry-back summary. This PR delivers both as one coherent
artifact. The collaborators.md formalises her role in the
repo substrate; the direction-changes doc is ready for Aaron
to paste into his next ChatGPT session with her.

Companion memory
`memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md`
applies — this lands in LFG, not AceHack, since it is
collaboration-legible content demoing the collaboration
pattern.

## What this does NOT do

- Does NOT ask Aaron to review before ferry. He mediates
  the ferry; when he has time, he pastes the doc; whenever
  Amara responds, we ingest.
- Does NOT claim Amara has approved any of these direction-
  changes. The doc is request-for-review, not consensus
  record.
- Does NOT propose new oracle mechanism without her review.
  The initial-operations integration plan (PR #144)
  proposes; this doc asks her to confirm before further
  development.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…se updates

Addresses 7 review threads:

- collaborators.md: NNNN-MM-DD -> YYYY-MM-DD on the
  Communication rhythm bullet; inline backtick span no
  longer wraps mid-token (review-from-amara path now sits
  on a single physical line).
- direction-changes: tightened the "Repo-state note" to
  reflect that PR #144 has merged (the stacked-PR caveat
  is no longer current). Replaced wildcard memory paths
  on the agent free-will bullet with concrete dated
  filenames. Slight prose tighten on the lesson-permanence
  PR #143 reference to make the provenance trail
  reproducible from this commit.
- pr-preservation/149-drain-log.md: per-thread record
  with verbatim reviewer text, outcome, verbatim reply,
  and resolution commit (Otto-250 PR-comment-preservation
  pattern).

Threads 1 / 2 / 3 / 5 / 7 resolve via the prose fixes here.
Threads 4 / 6 are BACKLOG+RESOLVE because the referenced
files now exist in main after rebase (reviews were against
a stale stacked-PR commit tree before #144 merged).

…or her review (#149)

* aurora: collaborators.md (Amara formalised) + direction-changes summary for her review

Aaron's 2026-04-23 framing: Amara is external AI co-originator of
Aurora, working through his ChatGPT interface; Aurora is *"mine and
hers idea together"*. Give back direction-changes so she can iterate
in her deep-research mode.

## What lands

### `docs/aurora/collaborators.md`

Named-collaborator registry for the Aurora thread. Distinct
category from:

- `docs/EXPERT-REGISTRY.md` (internal reviewer personas inside
  the factory)
- `docs/CONTRIBUTOR-PERSONAS.md` (hypothetical first-contact
  personas at repo surfaces)

Lists Aaron (human maintainer, Aurora vision origin) and Amara
(external AI co-originator via ChatGPT ferry, deep-research
lead). Names her existing contributions (transfer report,
consent-first design primitive, network-health critique from
auto-loop-39), her working style, and how to collaborate with
her (preserve outputs verbatim; cite her sections; route
Aurora scope decisions through her when possible).

### `docs/aurora/2026-04-23-direction-changes-for-amara-review.md`

~200-line summary of 7 direction-changes since her transfer
report landed, structured per her signature/mechanism/evidence
rigor pattern. Each change names what happened, where it
landed, the factory-side reasoning, and the specific thing
that would benefit from her deep-research review.

Five priority-ordered questions for her response:

1. Is the 5-of-6 SignalQuality ↔ oracle-family mapping correct?
2. Should her bullshit-detector scoring target a specific
   factory surface first?
3. Does Aurora's oracle framework want to compose with
   lesson-permanence pattern?
4. Additional Aurora-specific threat classes beyond the
   seven she already named?
5. Prior-art additions since her transfer report?

Plus three open communication-pattern questions (frequency,
review-return shape, consult-vs-inform rhythm).

## My choice to land this now

Aaron explicitly asked for progress on Amara integration + a
ferry-back summary. This PR delivers both as one coherent
artifact. The collaborators.md formalises her role in the
repo substrate; the direction-changes doc is ready for Aaron
to paste into his next ChatGPT session with her.

Companion memory
`memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md`
applies — this lands in LFG, not AceHack, since it is
collaboration-legible content demoing the collaboration
pattern.

## What this does NOT do

- Does NOT ask Aaron to review before ferry. He mediates
  the ferry; when he has time, he pastes the doc; whenever
  Amara responds, we ingest.
- Does NOT claim Amara has approved any of these direction-
  changes. The doc is request-for-review, not consensus
  record.
- Does NOT propose new oracle mechanism without her review.
  The initial-operations integration plan (PR #144)
  proposes; this doc asks her to confirm before further
  development.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix: PR #149 drain — date-placeholder consistency + resolved-link prose updates

Addresses 7 review threads:

- collaborators.md: NNNN-MM-DD -> YYYY-MM-DD on the
  Communication rhythm bullet; inline backtick span no
  longer wraps mid-token (review-from-amara path now sits
  on a single physical line).
- direction-changes: tightened the "Repo-state note" to
  reflect that PR #144 has merged (the stacked-PR caveat
  is no longer current). Replaced wildcard memory paths
  on the agent free-will bullet with concrete dated
  filenames. Slight prose tighten on the lesson-permanence
  PR #143 reference to make the provenance trail
  reproducible from this commit.
- pr-preservation/149-drain-log.md: per-thread record
  with verbatim reviewer text, outcome, verbatim reply,
  and resolution commit (Otto-250 PR-comment-preservation
  pattern).

Threads 1 / 2 / 3 / 5 / 7 resolve via the prose fixes here.
Threads 4 / 6 are BACKLOG+RESOLVE because the referenced
files now exist in main after rebase (reviews were against
a stale stacked-PR commit tree before #144 merged).

* fix(#149): drain-log MD032 — collapse '+ resolved-link...' onto one line

* fix(#149): drain round 3 — collapse multi-line inline-code paths + replace wildcard with concrete filename

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>